EVE Search - Announcement:Skill Queue Issues

Rexxar Santaro wrote:

Lquid Drisseg wrote:

This seems like a really really simple problem to fix going forward.

Why cant we just make this simple for everyone?

If you have skills in a queue, they train at the attribute level rate. If you "pause" your skillqueue or otherwise are not training anything and still subbed, just give accounts a calculated fair SP rate passively.

Just make SP accumulation a passive thing that you apply in chunks as you want to train skills.

ItGÇÖs very hard, a nightmare, for a developer to program and synchronize both CPU-server with a DB-server, considering every skill queue is a server real time thread (with own list of different skills). Also, while everyone can interact with that thread through: subscriptions, plexes, attributes, implants, skill extractors, skill injectors. For sure there are running over 100,000 live threads!

Dynamic multithreading server programing is among hardest types. One bit of leaked memory (TRUE or FALSE) can turn into hundreds of Gigabytes of leaked memory in one hour. As a result GÇô server shutdown or Try Catch exception, which will stop the problematic code.

To track and count the SP for everyone is possible after processing a gazzilion of data.

Author	Thread Statistics \| Show CCP posts - 1 post(s)
Lquid Drisseg KarmaFleet Goonswarm Federation 17	Posted - 2017.06.09 13:40:59 - [1] - Quote This seems like a really really simple problem to fix going forward. There are seemingly constant issues with the SP system. People unsubbing and still training, trying to fix that problem at 1AM and causing more headaches to fix, people's skill queues running out and it still not being enough of an incentive to care to login, the massive influx of petitions all of these things can seemingly cause. Why cant we just make this simple for everyone? If you have skills in a queue, they train at the attribute level rate. If you "pause" your skillqueue or otherwise are not training anything and still subbed, just give accounts a calculated fair SP rate passively. No more petitions for reimbursing SP, no more people complaining that their skill queues ran out or were paused on them by a not-fully-vetted patch script, no more excessive petitions taking up support staff's time trying to calculate the amount of SP that should be reimbursed. Just make SP accumulation a passive thing that you apply in chunks as you want to train skills.
Lquid Drisseg KarmaFleet Goonswarm Federation 17	Posted - 2017.06.09 13:58:05 - [2] - Quote Brutualis wrote: Lquid Drisseg wrote: Just make SP accumulation a passive thing that you apply in chunks as you want to train skills. It's not that simple; skill points relate directly to your active plugins, attributes, what you are training. It's part of what makes Eve so cool. Thanks CCP for sorting the ghost training thing out. Everything you said is absolutely not what makes eve cool. If you think the skill training system is what makes eve cool you might want to get your head examined.
Lquid Drisseg KarmaFleet Goonswarm Federation 17	Posted - 2017.06.09 14:40:08 - [3] - Quote Rexxar Santaro wrote: Lquid Drisseg wrote: This seems like a really really simple problem to fix going forward. Why cant we just make this simple for everyone? If you have skills in a queue, they train at the attribute level rate. If you "pause" your skillqueue or otherwise are not training anything and still subbed, just give accounts a calculated fair SP rate passively. Just make SP accumulation a passive thing that you apply in chunks as you want to train skills. ItGÇÖs very hard, a nightmare, for a developer to program and synchronize both CPU-server with a DB-server, considering every skill queue is a server real time thread (with own list of different skills). Also, while everyone can interact with that thread through: subscriptions, plexes, attributes, implants, skill extractors, skill injectors. For sure there are running over 100,000 live threads! Dynamic multithreading server programing is among hardest types. One bit of leaked memory (TRUE or FALSE) can turn into hundreds of Gigabytes of leaked memory in one hour. As a result GÇô server shutdown or Try Catch exception, which will stop the problematic code. To track and count the SP for everyone is possible after processing a gazzilion of data. I am a software developer. This is not a hard problem to solve. They already have it solved. Skill training is already a thing. It would not be hard to add in a base level of training that occurs regardless of your queued skills and attribute levels. Please don't claim this is a hard problem, especially when the vast majority of the actual hard work has already been implemented.